Hybris UX Api icon

Hybris UX Api

(0 reviews)

PATCH Appointment by Id

Update Order Details for the PR market

This API is used to update the technician appointment for particular Order.

GET /searchTimeSlot API should be executed before updating the appointment to get the available technician's timeslot.

Request

This section defines all the possible data structures sent by the client when consuming the method.

URL

https://[localhost]:[port]/ecom-ux/v1/PR/appointment/{id}

URL PARAMS

nametypedescriptionrequired
businessIdstring2 letter ISO 3166 country code (TT, BB, JM, PA, etc.) identifying the business unit.
Enum values:
BS-Bahamas
CO-Colombia
CO1-Colombia Zona Franca
CL-Chile
CR-Costa Rica
DO-Dominican Republic
GT-Guatemala
HN-Honduras
JM-Jamaica
PA-Panama
PR-Puerto Rico
SV-Salvador
Y
IdStringUpdating the order details by using OrderIdY
namevaluedescriptionrequired
client-idstringThe client_id identifying the channel. Minimum characters: 5Y
client-secretstringPassword associated with the client_id. Minimum characters: 5Y
X-Correlation-IDstringIdentifier that correlates HTTP request between a client and server.
Any identification model (UUDI, checksum, etc.) can be used, as long as it is a unique value to differentiate a transaction.
N
It is Mandatory for business
channelIdstringChannel to business:
By default we are passing channelId as ECOM & the expected Value will be: "ECOM"
Optional
lobstringIt defines the Line of Business Values,and the values are FIXED,PREPAID, POSTPAID . Expected value is FIXEDY

Mandatory Fields

OrderReasonCode, CampaignCode, JobType, RescheduleReason, orderId.

note Subresource in Request

NameTypeM/ODescription
OrderReasonCodeStringMSF is default value for self install.E1 for TechnicianVisit. Example:
{
"text": "SF",
"@type": "OrderReasonCode"
}
CampaignCodeStringMSF is default value for self install.000 for TechnicianVisit. Example:
{
"text": "SIN",
"@type": "CampaignCode"
}
JobTypeStringME1 is default value . Example:
{
"text": "E1",
"@type": "JobType"
}
RescheduleReasonStringMThe RescheduleReason value will be ‘CR’ Example:
{
"text": "CR",
"@type": "RescheduleReason"
}

Patch AppointmentById Request Body for PR Market:

{
    "validFor": {
        "startDateTime": "2023-10-05T08:00:00.000-04:00",
        "endDateTime": "2023-10-05T12:00:00.000-04:00"
    },
    "relatedParty": [
        {
            "role": "Technician",
            "id": "1000",
            "@referredType": "Technician"
        },
        {
            "role": "Sales Representative",
            "id": "54321",
            "@referredType": "SalesRepresentative"
        }
    ],
    "relatedEntity": [
        {
            "id": "1200052247691014",
            "name": "orderId"
        }
    ],
    "note": [
        {
            "text": "E1",
            "@type": "OrderReasonCode"
        },
        {
            "text": "ECO",
            "@type": "CampaignCode"
        },
        {
            "text": "NC",
            "@type": "JobType"
        },
        {
            "text": "CR",
            "@type": "RescheduleReason"
        }
    ]
}
Definitions

Each of the request parameters is detailed.

nametypedescriptionrequired
validFor.startDateTimestringDefines the start date time of appointmentM
validFor.endDateTimestringDefines the end date time of appointmentM
relatedParty[].idstringTechnician IDN
rolestringStatic Content as 'Technician'N
@referredTypestringStatic Content as 'Technician'N
relatedParty[].idstringSalesRepresentative IDN
rolestringStatic Content as 'SalesRepresentative'N
@referredTypestringStatic Content as 'SalesRepresentative'N
relatedEntity[].idstringDefines the customer order idM
relatedEntity[].namestringStatic Content as 'Order Id'N

Response

In this section all the possible data structures received by the client at the moment of responding the method are defined.

Possible response success

This section defines all the possible data structures received by the client and that must be considered satisfactory at the time of responding to the method.

[ 200 ]

Created - Resource created successfully, response body contains an entity corresponding to the requested resource.


{
    "id": "12000522476910140001",
    "status": "R",
    "externalId": "112368",
    "validFor": {
        "startDateTime": "2023-10-05T08:00:00.071-04:00",
        "endDateTime": "2023-10-05T12:00:00.071-04:00"
    },
    "relatedParty": [
        {
            "role": "Technician",
            "id": "1000",
            "@referredType": "Technician"
        },
        {
            "role": "Sales Representative",
            "id": "54321",
            "@referredType": "Sales Representative"
        }
    ],
    "relatedEntity": [
        {
            "id": "1200052247691014",
            "name": "OrderID"
        }
    ],
    "note": [
        {
            "id": "E1",
            "name": "OrderReasonCode"
        },
        {
            "id": "ECO",
            "name": "CampaignCode"
        },
        {
            "id": "NC",
            "name": "JobType"
        },
        {
            "id": "CR",
            "name": "RescheduleReason"
        },
        {
            "id": "001",
            "name": "TotalUnits"
        }
    ]
}

Possible Status Code

Status CodeDescription
AASSIGNED
BNO MONEY
CCOMPLETE
DDOOR HANGR LEFT
ENO ACCESS
FAM FOLLOW-UP
GCMPL O/THAN ORD
HHOLD
IIN-SERVICE
LCANNOT LOCATE
MPM FOLLOW-UP
NNO MANGR AVAIL
OOPEN
PPRINTED
QSEE HOUSE
RRESCHEDULE
SNON PAY SAVE
XCANCEL

Possible RescheduleReason Values

RescheduleReason CodeDescription
A1ATTEMPT#1
A2ATTEMPT#2
A3ATTEMPT#3
CRCUST. REQUESTED
D3DOCSIS 3 SPLIT
EQEQP NOT AVAIL
FRFINANCE REASON
MRRELATED MS/MR
NANO ADULT
NBNO PERMISSION
NCNEEDS CUST WORK
NHNOT AT HOME
NKNO PARKING
NRWEATHER CONDITN
NTNO TIME TO DO
RAREQ. TAP AUDIT
RBREQ BUCKET TRUK
RCREQ. CONDUIT
RGREQ. GUINDOLA
RMREQ MAINTENAN
RSRESCH PER SYS
RTREQ. TRENCH
SDSAME DAY SERV
VAVERIFY ADDRESS

Possible response error

In this section all the possible data structures received by the client are defined and that must be considered as unsatisfactory when responding to the method.

[ 400 ]

Bad Request - the request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

{
  "errors" : [{
      "code" : 400 ,
      "message" : "The request is invalid or not properly formed.",
      "description" : "The client sent too many requests and server is not able to serve them all at the moment"
    }
  ]
}
[ 501 ]

Not implemented - indicates that the server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.

{
  "errors" : [{
      "code" : 501,
      "message" : "NOT IMPLEMENTED",
      "description" : "Operation GET /reset for Business Id: PR not implemented"
    }
  ]
  }

Reviews